Systems and methods for communicating with a unique identifier

ABSTRACT

A system for device communication is disclosed. The system may include one or more memory devices storing instructions and one or more processors configured to execute the instructions to transmit a first unique identifier to a wave device, and receive a second unique identifier from the wave device. Further, the first unique identifier may exclusively identify a person, and the second unique identifier may exclusively identify a first wave receiver associated with a person, an entity, a place, or an object. In addition, at least the first unique identifier may be transmitted to the wave device based on an indication of a proximity between the first person and the first wave receiver.

PRIORITY CLAIM

This disclosure claims priority under 35 U.S.C. § 119 to U.S.Provisional Patent Application No. 62/002,419 filed on May 23, 2014, andentitled “Systems and Methods for Communicating with a UniqueIdentifier” and U.S. Provisional Patent Application No. 62/022,738 filedon Jul. 10, 2014, and entitled “Systems and Methods for Providing anInteractive Community Through Device Communication.” The aforementionedapplications are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The disclosed embodiments generally relate to systems and methods fordevice communication, and more particularly, systems and methods forproviding device communications based on one or more unique identifiers.

BACKGROUND

Computers have become integral to the way people communicate with oneanother. In particular, certain computer-enabled communications, such asemail, text messaging, social media, and the like, have become theprimary means through which certain people, such as friends, family,coworkers etc., communicate. However, in general, these types ofcommunication require a person to stop and consider what it is they wantto communicate before doing so.

Computers also have the capability to gather information about anindividual automatically. For example, mobile devices are able todetermine location-based information, such as the location of the deviceoperated by the user and what other user-operated devices are nearby. Inthis way, computers are able to gather information associated with theperson or entity operating these devices in order to contextualize thegathered information. While some forms of communication currentlyinclude background information along with a message (e.g., a socialmedia post that identifies the poster's location), current systems andprocesses do not adequately utilize contextual information to facilitatecommunication.

SUMMARY

The disclosed embodiments include systems and methods that enablecommunication through the transmission and/or receipt of a uniqueidentifier.

Consistent with a disclosed embodiment, a system for devicecommunication is provided. The system may include one or more memorydevices storing instructions and one or more processors configured toexecute the instructions to transmit a first unique identifier to a wavedevice, and receive a second unique identifier from the wave device.Further, the first unique identifier may exclusively identify a person,and the second unique identifier may exclusively identify a first wavereceiver, the first wave receiver associated with a person, an entity, aplace, or an object. In addition, at least the first unique identifiermay be transmitted to the wave device based on an indication of aproximity between the first person and the first wave receiver.

Consistent with another disclosed embodiment, a computer-implementedmethod of device communication is provided. The method may includetransmitting, by one or more processors, a first unique identifier to awave device, and receiving a second unique identifier from the wavedevice. The method may also include receiving a payload from the wavedevice, wherein the payload includes a list of unique identifierspreviously received by the wave device. The method may further includeadding the second unique identifier and the list of unique identifierspreviously received by the wave device to a list of received uniqueidentifiers.

Consistent with yet another disclosed embodiment, a data collectiondevice is provided. The data collection device may include one or morememory devices storing instructions, and one or more processorsconfigured to execute the instructions to receive a unique identifierfrom a wave device. The one or more processors may be further configuredto execute the instructions to determine that the unique identifier isincluded in a list of received unique identifiers, determine an actionto be triggered based on the unique identifier, and provide informationto the wave device for triggering the action.

Although disclosed embodiments are discussed primarily in the context ofmobile devices and software instructions that are executed by thosemobile devices, other implementations are contemplated. For example,disclosed embodiments may include software instructions that areexecuted by a computing system, such as a desktop computer, a laptop,etc. Moreover, the configuration and architecture, etc. of the computingsystems, mobile or non-mobile, are not limiting to the disclosedembodiments. Systems or components that execute software instructions toperform one or more operations consistent with the disclosed embodimentsand/or store information generated and/or used by the disclosedembodiments, may be particularly configured to perform the one or moreparticular operations consistent with the disclosed embodiments.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 illustrates an exemplary system consistent with disclosedembodiments;

FIG. 2 is a block diagram of an exemplary client device computingsystem, consistent with disclosed embodiments;

FIG. 3 is a block diagram of an exemplary computing system, consistentwith disclosed embodiments;

FIG. 4 illustrates an exemplary unique identifier system, consistentwith disclosed embodiments;

FIG. 5 is a flowchart of an exemplary automatic wave interactionprocess, consistent with disclosed embodiments; and

FIG. 6 is a flowchart of an exemplary wave interaction enhancingprocess, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

Disclosed embodiments pertain to device communication that isfacilitated through the use of one or more unique identifiers. A uniqueidentifier may be any information (e.g., an alphanumeric string) that isunique to and exclusively identifies an associated person, entity (e.g.,business, merchant, corporation, community, event, etc.), place (e.g.,building, room, home, landmark, monument, country, city, neighborhood,street, etc.), and/or object (e.g., product, vehicle, apparel, etc.).

The disclosed embodiments may execute software that, when executed byone or more processors, perform processes that provide uniqueidentifier(s) that may be used to facilitate communications betweenremote devices or other components. For instance, consistent withdisclosed embodiments, interactions that occur between one or morepeople, entities, places, and/or objects may include the transmissionand/or receipt of one or more unique identifiers via system componentsexecuting software to perform processes that provide suchcommunications.

For example, the disclosed embodiments may allow automatedcommunications between devices that reflect interactions between one ormore people, entities, places, and/or objects. These interactions mayinclude, for example, coworkers having such devices on their personpassing each other in the hallway, drivers of vehicles including suchdevices passing each other on the street, a customer having such adevice on their person entering a merchant location including anothersuch device, a person having such a device entering a room configuredwith another such device, a person having such a device in proximity ofa television, signage, or other type of display device showing anadvertisement, a group of people having respective such devicesattending a meeting, a person having such a device who is attending aconcert, a tourist having such a device visiting a landmark, a passengerentering a vehicle, and the like. In some embodiments, an interactionmay be recorded after an interaction between one or more people,entities, places, and/or objects, such as when a person involved in theinteraction does not have a device with them during the interaction, andinstead inputs the information at a later time.

Through receipt and transmission of unique identifiers, interactions maybe enhanced to include the sharing, recording, and/or analyzing ofinformation, including information identifying that the interactionoccurred, whether or not any people involved in the interaction wereaware of it.

In one aspect, an interaction may result in a computing device receivinga unique identifier. For example, a person may be involved in aninteraction that results in an associated computing device receiving aunique identifier. The computing device may be configured to perform oneor more processes to use the unique identifier in manners consistentwith disclosed embodiments. For example, the computing device mayreceive and store the received unique identifier. In another aspect, thecomputing device may be configured to receive and store contextualinformation, such as when (e.g., time, date, day of week, month, year,etc.) and where (e.g., geographic location information, etc.) the uniqueidentifier was received. The computing device may also perform a processto match the unique identifier to stored information, which thecomputing device may use to trigger an action (e.g., display informationto a user). The computing device may also add the unique identifier to ahistorical list of received unique identifiers.

In another aspect, the disclosed embodiments may be configured toidentify an interaction, such as those exemplified above, which mayresult in a computing device transmitting a unique identifier to anotherdevice. For example, a person having a computing device configured inaccordance with disclosed embodiments may be involved in an interactionthat results in a unique identifier associated with the person beingtransmitted and received by another device. The receiving device may usethe unique identifier to perform one or more processes, such as thosedescribed above. One or more of these processes may include forwardingthe unique identifier to another device, which may also be configured toperform processes that use the unique identifier. This cycle maycontinue, such that a unique identifier may be involved in any number ofinteractions that may or may not involve the underlying person, entity,place, or object that is associated with the unique identifier. Forinstance, the disclosed embodiments may include systems and methods thatgenerate a unique identifier that may be provided from a first device toa second device based on a determined interaction, the provision of theunique identifier occurring during a first level of communications. Inturn, the disclosed embodiments may include configurations where thesecond device may further provide the unique identifier to a thirddevice during a second level of communications, and so on.

A computing device may be configured to receive and/or transmit a uniqueidentifier in a variety of manners. In one exemplary embodiment, two ormore proximate devices may automatically communicate with each other toexchange unique identifiers. A first device may automatically connect toa second device (e.g., via a network or direct connection between thefirst and second devices using, for example, Bluetooth®, WiFi, RFID,etc.) when the devices are within a certain proximity to each other. Thefirst device may “wave” to the second device, including sending a uniqueidentifier to the second device. The second device may “wave back” tothe first device, including sending a different unique identifier backto the first device.

Each of the first and second devices may perform one or more processesusing the respectively received unique identifier. In addition, thefirst and second devices may exchange additional data. For example, thefirst and second devices may additionally or alternatively exchange oneor more messages. In another example, the first and second devices mayexchange respective historical lists of received unique identifiers,thereby transmitting unique identifiers that are not associated with anypeople, entities, places, or objects that are involved in theinteraction.

Consistent with disclosed embodiments, a data collection device maystore information in association with one or more unique identifiers.For example, the data collection device may store software instructionsthat are executed by a processor to perform an action that may betriggered as a result of a computing device receiving a particularunique identifier. In another example, the data collection device maystore a user profile associated with a unique identifier. The datacollection device may store as part of the user profile additionalinformation that a computing device may use to determine an action to betriggered when another unique identifier is received. The datacollection device may also store as part of the user profile ahistorical list of received unique identifiers, as well as informationassociated with computing devices that have received the uniqueidentifier associated with the user profile. In this way, a person mayoperate a computing device to find out about interactions that involvedtheir unique identifier, including interactions with which they were notdirectly involved.

FIG. 1 is a diagram illustrating an exemplary system 100 for performingone or more operations consistent with the disclosed embodiments. In oneembodiment, system 100 may include a plurality of wave devices 110 and120, a data collection device 140, and a network 150. The components andarrangement of the components included in system 100 may vary. Thus,system 100 may further include other components that perform or assistin the performance of one or more processes consistent with thedisclosed embodiments. For example, while two wave devices 110 and 120are depicted, it should be understood that any number of wave devices120 may be included in system 100.

Wave devices 110 and 120 may each be one or more computing devices thatare configured to execute software instructions for performing one ormore operations consistent with the disclosed embodiments. In anexemplary embodiment, a “wave device” is any device that is capable ofreceiving and/or transmitting a unique identifier. Wave devices 110, 120may be any type of computing device, such as a mobile device (e.g.,smart phone, tablet, etc.), laptop, desktop computer, server, beacon,sensor device, and/or any device capable of communicating with anotherdevice, such as a Bluetooth®-enabled device, WiFi-enabled device, RFIDchip, etc.

In some embodiments, wave device 110 may include one or more processorsconfigured to execute software instructions stored in memory, such asmemory included in wave device 110. Wave device 110 may include softwarethat when executed by one or more processors performs knownInternet-related communications and content display processes. Forinstance, wave device 110 may execute browser software that generatesand displays interfaces including content on a display device includedin, or connected to, wave device 110.

Wave device 110 may be configured to store a unique identifierassociated with a person, entity, place, or object. Wave device 110 maystore the unique identifier in a memory device. Wave device 110 maystore the unique identifier as part of a unique identifier (UID)profile. Wave device 110 may be configured to transmit the uniqueidentifier to other devices, such as wave device 120 and/or datacollection device 140, via network 150.

In some embodiments, wave device 120 may also include one or moreprocessors configured to execute software instructions stored in memory,such as memory included in wave device 120. Wave device 120 may comprisecomponents and perform operations that are the same or similar to wavedevice 110. For example, wave device 120 may be configured to store aunique identifier associated with a different person, entity, place, orobject. Wave device may also store the unique identifier as part of aUID profile and be configured to transmit the unique identifier to otherdevices, such as wave device 110 and/or data collection device 140, vianetwork 150. It should be understood however, that wave devices 110 and120 may be configured differently. For example, one or more of wavedevices 110, 120 may be configured to only receive or only transmit aunique identifier.

Data collection device 140 may include one or more computing systemsthat are configured to execute software instructions stored on one ormore memory devices to perform one or more operations consistent withthe disclosed embodiments. For example, data collection device 140 mayinclude one or more memory device(s) storing data and softwareinstructions and one or more processor(s) configured to use the data andexecute the software instructions to perform server-based functions andoperations known to those skilled in the art and related to the functionand operations associated with data collection device 140. Moreover, incertain embodiments, data collection device 140 may be configured toexecute software instructions that interact with software program(s)stored and executed by wave device 110 and/or wave device 120, such as amobile application that is executed on a mobile device.

Data collection device 140 may be a general purpose computer, amainframe computer, or any combination of these components. In certainembodiments, data collection device 140 (or a system including datacollection device 140) may be configured as a particular apparatus,system, and the like based on the storage, execution, and/orimplementation of the software instructions that perform one or moreoperations consistent with the disclosed embodiments. Data collectiondevice 140 may be standalone, or it may be part of a subsystem, whichmay be part of a larger system. For example, data collection device 140may represent distributed servers that are remotely located andcommunicate over a network (e.g., network 150).

In an exemplary embodiment, data collection device 140 may include ormay connect to one or more storage devices configured to store dataand/or software instructions used by one or more processors of datacollection device 140 to perform operations consistent with disclosedembodiments. For example, data collection device 140 may include memoryconfigured to store one or more software programs that performs severalfunctions when executed by a processor. The disclosed embodiments arenot limited to separate programs or computers configured to performdedicated tasks. For example, data collection device 140 may includememory that stores a single program or multiple programs. Additionally,data collection device 140 may execute one or more programs locatedremotely from data collection device 140. For example, data collectiondevice 140 may access one or more remote programs stored in memory of aremote component that, when executed, perform operations consistent withthe disclosed embodiments.

In an exemplary embodiment, data collection device 140 may storeinformation associated with unique identifiers, such as UID profiles.The UID profiles may include information identifying a person, entity,place, or object that is associated with the UID profile and theassociated unique identifier. The UID profiles may also includeinformation associated with interactions involving transmission of theassociated unique identifier and/or receipt of another uniqueidentifier. In addition, the UID profiles may include instructions forone or more actions to be triggered based on particular interactionsthat occur. For example, UID profiles may include instructions foractions to be triggered when a computing device receives the associatedunique identifier and/or actions to be triggered when a computing deviceassociated with the unique identifier receives another uniqueidentifier.

In certain embodiments, data collection device 140 may be a component ofone or more of wave device 110 and wave device 120. For example, wavedevice 110 and/or wave device 120 may include components configured toperform one or more of the processes of data collection device 140. Forinstance, wave device 120 may be configured to store informationassociated with a UID profile.

In certain embodiments, wave device 110 and/or wave device 120 mayconnect to data collection device 140 to retrieve information storedtherein. For example, wave device 110 may access information associatedwith interactions that occurred that involved a transmission and/orreceipt of a unique identifier, such as transmission of a uniqueidentifier associated with a person operating wave device 110. Inanother example, wave device 110 may connect to data collection device140 to provide information to be stored by data collection device 140.

Network 150 may be any type of network configured to providecommunications between components of system 100. For example, network150 may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as a Wide Area Network, a Local Area Network, adirect connection, or other suitable connection(s) that enables thesending and receiving of information between the components of system100. For example, network 150 may facilitate connection via Bluetooth®,WIFI, RFID, NFC, radio, Ethernet, Internet, magnetic devices, infraredtechnology, etc.

FIG. 2 shows an exemplary mobile device 210, consistent with disclosedembodiments. In certain embodiments, mobile device 210 may embody wavedevice 110 and/or 120. It should be understood, however, that mobiledevice 210 may also embody data collection device 140 and/or a componentnot shown in FIG. 1. In one embodiment, mobile device 210 may includeone or more processors 221, one or more input/output (I/O) devices 222,and one or more memories 223. In one embodiment, mobile device 210 maytake the form of a general purpose computer, a mainframe computer, orany combination of these components. In some embodiments, mobile device210 may be a personal computing device, such as a smartphone, tablet,laptop, desktop computer, etc.

In certain embodiments, mobile device 210 (or a system including mobiledevice 210) may be configured as a particular apparatus, system, and thelike based on the storage, execution, and/or implementation of thesoftware instructions that perform one or more operations consistentwith the disclosed embodiments. Mobile device 210 may be standalone, orit may be part of a subsystem, which may be part of a larger system.

Processor 221 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems. The disclosed embodimentsare not limited to any type of processor(s) configured in mobile device210.

I/O devices 222 may be one or more device that is configured to allowdata to be received and/or transmitted by mobile device 210. I/O devices222 may include one or more digital and/or analog communication devicesthat allow mobile device 210 to communicate with other machines anddevices, such as other components of system 100.

Memory 223 may include one or more storage devices configured to storeinstructions used by processor 221 to perform functions related to thedisclosed embodiments. For example, memory 223 may be configured withone or more software instructions, such as program(s) 224 that mayperform one or more operations when executed by processor 221. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 223 mayinclude a single program 224 that performs the functions of mobiledevice 210, or program 224 could comprise multiple programs.Additionally, processor(s) 221 may execute one or more programs locatedremotely from mobile device 210. For example, mobile device 210, mayaccess one or more remote programs that, when executed, performfunctions related to certain disclosed embodiments.

Memory 223 may also store data 225 that may reflect any type ofinformation in any format that the system may use to perform operationsconsistent with the disclosed embodiments. For example, data 225 mayinclude a unique identifier associated only a particular mobile device210. Data 225 may also include stored information, such as informationassociated with an event to be triggered based on data communicationsreceived by mobile device 210.

In certain embodiments, memory 223 may store a mobile application 226.Mobile application 226 may be one or more programs or softwareinstructions that, when executed by processor(s) 221, perform one ormore operations associated with an entity associated with mobileapplication 226, such as a merchant or financial service provider. Forexample, mobile application 226 may be a mobile application that isstored in a mobile device (e.g., mobile device 210) that performsoperations and generates interface(s) that are displayed on a displaydevice of mobile device 210. The interface(s) may be configured topresent information and provide request(s) that elicit input from auser. Mobile device 210 may be configured with known input hardware andsoftware components that accept input from a user through known mobiledevice mechanisms, such as touch screen technologies, voice input,keypad entry, etc.

Mobile application 326 may be configured to use information to generateinformation, analyze and determine condition(s), generate results basedon those condition(s), and provide data and interface(s) including thedata. In certain aspects, mobile application 226 may be configured toperform one or more processes consistent with the disclosed embodiments,such as, for example, determining information to be displayed to a user,stored in a memory, and/or transmitted to another device as a result ofreceiving a unique identifier.

FIG. 3 shows an exemplary computing system including server 310,consistent with disclosed embodiments. In an exemplary embodiment,server 310 may embody data collection device 140. It should beunderstood, however, that the configuration and components of server 310may additionally or alternatively represent that of wave device 110,wave device 120, and/or a component not shown in FIG. 1.

In one embodiment, server 310 may include one or more processors 321,one or more input/output (I/O) devices 322, and one or more memories323. Alternatively, server 310 may take the form of a general purposecomputer, a mainframe computer, or any combination of these components.In certain embodiments, server 310 (or a system including server 310)may be configured as a particular apparatus, system, and the like basedon the storage, execution, and/or implementation of the softwareinstructions that perform one or more operations consistent with thedisclosed embodiments. Server 310 may be standalone, or it may be partof a subsystem, which may be part of a larger system.

Processor 321 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMID™, or any of variousprocessors manufactured by Sun Microsystems. The disclosed embodimentsare not limited to any type of processor(s) configured in server 310.

I/O devices 322 may be one or more device that is configured to allowdata to be received and/or transmitted by server 310. I/O devices 322may include one or more digital and/or analog communication devices thatallow server 310 to communicate with other machines and devices, such asother components of systems 100.

Memory 323 may include one or more storage devices configured to storeinstructions used by processor 321 to perform functions related todisclosed embodiments. For example, memory 323 may be configured withone or more software instructions, such as program(s) 324 that mayperform one or more operations when executed by processor(s) 321. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 323 mayinclude a single program 324 that performs the functions of the server311, or program 324 could comprise multiple programs. Additionally,processor 321 may execute one or more programs located remotely fromserver 311. For example server 310, may access one or more remoteprograms that, when executed, perform functions related to certaindisclosed embodiments.

Memory 323 may also store data 325 that may reflect any type ofinformation in any format that the system may use to perform operationsconsistent with the disclosed embodiments. For example data 325 mayinclude stored user information associated with one or more uniqueidentifiers.

Server 310 may also be communicatively connected to one or moredatabase(s) 326. Server 310 may be communicatively connected todatabase(s) 326 through network 150. Database 326 may include one ormore memory devices that store information and are accessed and/ormanaged through server 310. By way of example, database(s) 326 mayinclude Oracle™ databases, Sybase™ databases, or other relationaldatabases or non-relational databases, such as Hadoop sequence files,HBase, or Cassandra. The databases or other files may include, forexample, data and information related to the source and destination of anetwork request, the data contained in the request, etc. Systems andmethods of disclosed embodiments, however, are not limited to separatedatabases. In one aspect, server 310 as exemplified in FIG. 3 mayinclude database 326. Alternatively, database 326 may be locatedremotely from the server 310. Database 326 may include computingcomponents (e.g., database management system, database server, etc.)configured to receive and process requests for data stored in memorydevices of database(s) 326 and to provide data from database 326.

Wave devices 110 and 120 may be configured as mobile device 210, server310, or another computing device that includes one or more of thecomponents of mobile device 210 and/or server 310. Regardless of theirparticular configuration, wave devices 110 and 120 may be configured totake part in a wave interaction. A “wave interaction” may be anyinteraction between a person, entity, place, or object and anotherperson, entity, place, or object that results in a wave device receivingand/or transmitting a unique identifier.

For example, a person carrying wave device 110 may walk past a personcarrying wave device 120. As a result, wave device 110 and wave device120 may automatically connect to each other via network 150 (e.g., via aBluetooth® connection) and exchange unique identifiers respectivelystored thereon. It should be understood, however, that receipt and/ortransmission of a unique identifier may not necessary occur during aninteraction. For example, a user may operate a computing device tomanually transmit a unique identifier to another computing device afteran interaction occurs.

While wave devices 110 and 120 have been described, it should beunderstood that any number of wave devices may be included in system100. Each wave device may be configured to take part in a waveinteraction to receive and/or transmit a unique identifier. Each wavedevice may be configured to subsequently perform one or more processesassociated with the wave interaction. For example, each wave device maystore information (e.g., in an associated memory, in data collectiondevice 140, etc.) associated with the wave interaction, such as when andwhere the wave interaction occurred, as well as any unique identifiersreceived as a result of the wave interaction. In another example, eachwave device may transmit additional information to another wave deviceas a result of a wave interaction.

FIG. 4 is an exemplary diagram of a unique identifier (UID) system 400depicting an exemplary interrelationship between unique identifiers, UIDprofiles, wave devices, a data collection device, and people, entities,places, and objects associated with the unique identifiers. As has beendescribed, a unique identifier may be any information that is unique toand exclusively identifies an associated person, entity, place, and/orobject. For example, each unique identifier may be a systematically-and/or randomly-assigned alphanumeric string configured to be received,stored, and transmitted as data. In certain aspects, data collectiondevice 140 may be configured to execute software instructions thatperform unique identifier assigning processes that assign a person,place, entity or object with a unique identifier and store theinformation in a data structure stored in a memory device(s).

As exemplified in FIG. 4, data collection device 140 (or anothercomponent) may associate a person 406 with a unique identifier 407(e.g., “UID01”). Unique identifier 407 may be “unique” to andexclusively identify person 406. Person 406 may also be associated withone or more wave devices 410. For example, person 406 may own, carry,possess, or otherwise control one or more computing devices configuredto be used in a wave interaction to transmit unique identifier 407 toanother device and/or receive another unique identifier.

One or more of wave devices 410 may be configured to store uniqueidentifier 407 as part of a UID profile 408. UID profile 408 may includeone or more programs and/or data stored in a memory associated with wavedevice 410 and configured to associate person 406, unique identifier 407and wave device 410. By associating person 406, unique identifier 407,and wave device 410, interactions involving person 406 may be defined aswave interactions through wave device 410 transmitting unique identifier407 to another wave device. For example, when person 406 moves to withina certain proximity of another person (an “interaction”), a wave device410 may come into proximity with a wave device associated with the otherperson. Wave device 410 may connect to the other wave device andtransmit unique identifier 407 to the other wave device (thus theinteraction is a “wave interaction”).

In some embodiments, UID profile 408 may include additional informationassociated with person 406 and/or unique identifier 407. For example,UID profile 408 may include a historical list of received uniqueidentifiers (“UID receipt history”). For example, the UID receipthistory may include all unique identifiers that were received by a wavedevice 410 as a result of a wave interaction involving person 406. Itshould be understood that UID receipt history may not be limited tounique identifiers received by one wave device 410, and instead mayinclude all unique identifiers received by all wave devices 410associated with person 406 and unique identifier 407.

In another example, UID profile 408 may include additional informationconfigured to be transmitted to another wave device as a result of awave interaction. For example, UID profile may include a payload 409.Payload 409 may include data that may be selectively transmitted toanother device as a result of a wave interaction. For example, payload409 may include a message to be transmitted to another wave device andused by the other wave device in one or more processes. The message mayinclude, for example, textual data, image data, video data, audio data,program instructions, etc., which the other wave device may use todisplay a textual message, an image, a video, play audio, executeprogram instructions, etc.

In another example, payload 409 may include a UID receipt history. Thatis, in addition to transmitting unique identifier 407 to another wavedevice, a wave device 410 may transmit a UID receipt history as part ofa payload 409. In this way, the other wave device may receive uniqueidentifier 407 and a list of unique identifiers that were received as aresult of wave interactions involving person 406.

In some embodiments, a wave device 410 may be configured to perform oneor more processes to determine a payload 409 to be transmitted toanother wave device as a result of a wave interaction. For example, awave device 410 may customize payload 409 depending on other availableinformation. In one example, wave device 410 may determine data to beincluded as part of a payload 409 based on time, date, and/or locationdata. In this way, wave device 410 may customize payloads 209 dependingon when and where a corresponding wave interaction occurs.

In another example, wave device 410 may be configured to customize apayload 409 based on a unique identifier received as a result of a thecorresponding wave interaction. For example, wave device 410 may match areceived unique identifier to stored information and customize payload409 based on the stored information. For example, wave device 410 maymatch a receive unique identifier to information identifying a personassociated with the received unique identifier, and customize payload409 to include a textual message that includes the identified person'sname.

While only one person 406 is depicted, it should be understood that anynumber of people may be included in UID system 400. Each person may beassociated with a unique identifier and one or more wave devices insubstantially the same manner as person 406, unique identifier 407, andwave devices 410. As people interact with each other, wave interactionsmay occur between their wave devices, causing unique identifiers andpayloads to be transmitted and/or received as a result.

UID system 400 may also include entities associated with uniqueidentifiers and wave devices. As used herein, an “entity” refers to anorganization of one or more people that is separately identifiableindependent of the one or more people. For example, an entity may be,for example, a business, a merchant, a corporation, a brand, acommunity, an event, and/or the like.

As shown in FIG. 4, an entity 411 may be associated with a uniqueidentifier 412 (e.g., “UID02”). Unique identifier 412 may be “unique” toand exclusively identify entity 411. Entity 411 may also be associatedwith one or more wave devices 415. For example, wave devices 415 may bearranged such that a wave interaction involving a wave device 415reflects an interaction with entity 411. For example, a wave device 415may be a computing device controlled by a person associated with entity411, such as an employee, representative, official, etc. In anotherexample, a wave device 415 may be a computing device located within asetting associated with entity 411, such as a place of business. Wavedevices 415 may store a UID profile 413 that associates correspondingwave device 415 with unique identifier 412 and entity 411.

In one example, entity 411 may be a merchant. The merchant may be anyentity that may offer any type of product or service. The merchant mayinclude brick and mortar location(s) that a consumer may physicallyvisit and purchase goods and services and/or office-type buildings. Suchphysical locations may include back and/or front-end computingcomponents that store data and execute software instructions to performoperations consistent with disclosed embodiments, such as computers thatare operated by employees of the merchant (e.g., back office systems,etc.). In some instances, the merchant may be a financial serviceprovider, such as a bank, credit card issuer, or other type of financialservice entity that offers, issues, generates, provides, manages, and/ormaintains financial service accounts for one or more users.

Entity 411 (e.g., a person associated with entity 411) may position wavedevices 415 such that they are configured to be involved in waveinteractions with other wave devices. For example, in the example inwhich entity 411 is a merchant, the merchant may place a wave device 415in a retail store location. The wave device 415 may be configured tocommunicate with other wave devices (e.g., wave devices 410) that enterthe retail store to transmit unique identifier 412 to the other wavedevices and/or receive a unique identifier from the other wave devices.In this way, interactions such as people entering a retail store may bewave interactions.

Wave interactions between a wave device 415 and another wave device(e.g., a wave device 410) may occur in a manner that is the same as orsimilar to the exemplary wave interactions described above with respectto wave devices 410. For example, in addition to the transmission and/orreceipt of a unique identifier, wave interactions involving wave devices415 may include transmission of a payload 414 stored as part of UIDprofile 413.

Payload 414 may include data to be transmitted to other wave devices tocommunicate additional information. For example, payload 414 may includea message to be transmitted to another wave device. In another example,payload 414 may include a UID receipt history that includes a list ofunique identifiers received by wave device 415. Through transmission ofpayload 414 from a wave device 415 to another wave device, informationassociated with entity 411 may be communicated to people through waveinteractions. For example, wave device 415 may transmit a greeting to acustomer's wave device when the customer enters a retail store. Inanother example, wave device 415 may transmit a message that includescustomized information, such as daily specials, coupons, hours ofoperation, wait times, etc.

UID system 400 may also include places associated with uniqueidentifiers and wave devices. As used herein, a “place” refers to aphysical location that has some identifiable feature that defines thelocation. Examples of a place may include a landmark, a monument, acountry, a city, a neighborhood, a street, a building, a home, a room,and/or the like.

As shown in FIG. 4, a place 416 may be associated with a uniqueidentifier 417 (e.g., “UID03”). Unique identifier 417 may be “unique” toand exclusively identify place 416. Place 416 may also be associatedwith one or more wave devices 420. For example, wave devices 420 may bearranged such that a wave interaction involving a wave device 420reflects an interaction with place 416. For example, a wave device 420may be a computing device located near and/or within a boundary of place416 and/or configured to connect to other wave devices that are nearand/or located within a boundary of place 416. Wave devices 415 maystore a UID profile 418 that associates corresponding wave device 420with unique identifier 417 and place 416.

In one example, place 416 may be a landmark (e.g., the Liberty Bell, theNorth Pole, the Washington Monument, the Golden Gate Bridge, etc.). Aperson (e.g., a person associated with the landmark, such as anauthority employee, official, representative, etc.) may position a wavedevice 420 to interact with other wave devices that are located within acertain proximity to the landmark. In this way, wave device 420 may beinvolved in wave interactions that result from a person interacting withthe landmark (e.g., visiting the landmark).

Wave interactions between a wave device 420 and another wave device(e.g., a wave device 410) may occur in a manner that is the same as orsimilar to the exemplary wave interactions described above with respectto wave devices 410 and 415. For example, in addition to thetransmission and/or receipt of a unique identifier, wave interactionsinvolving wave devices 420 may include transmission of a payload 419stored as part of UID profile 418.

Payload 419 may include data to be transmitted to other wave devices tocommunicate additional information. For example, payload 419 may includea message to be transmitted to another wave device. In another example,payload 419 may include a UID receipt history that includes a list ofunique identifiers received by wave device 420. Through transmission ofpayload 419 from a wave device 420 to another wave device, informationassociated with place 416 may be communicated to people through waveinteractions. For example, wave device 420 may transmit historicalinformation associated with a landmark to a tourist's wave device whenthe tourist reaches a landmark. The wave device may be configured todisplay the historical information on a display device for viewing bythe tourist.

UID system 400 may also include objects associated with uniqueidentifiers and wave devices. In one embodiment, an “object” may be anyphysical, identifiable object. In an exemplary embodiment, “object” mayrefer to a readily movable object, although the term is not limitedthereto. Examples of objects that may be present in UID system 40 mayinclude vehicles, retail products, historically-significant objects,and/or the like. In another example, an object may be a wave device.

As shown in FIG. 4, an object 421 may be associated with a uniqueidentifier 422 (e.g., “UID04”). Unique identifier 422 may be “unique” toand exclusively identify object 421. Object 421 may also be associatedwith one or more wave devices 425. For example, wave devices 425 may bearranged such that a wave interaction involving a wave device 425reflects an interaction with object 421. For example, a wave device 425may be a computing device physically associated and/or in dose proximityto object 421 such that interactions with object 421 (e.g., a personbeing near object 421) may be wave interactions between wave device 425and another wave device associated with a person, entity, or placeinvolved in the interaction. Wave devices 425 may store a UID profile423 that associates corresponding wave device 425 with unique identifier422 and place 421.

In one example, object 421 may be a vehicle. A person (e.g., a personassociated with the vehicle, such as driver, owner, etc.) may position awave device 425 to interact with other wave devices that are locatedwithin a certain proximity to the vehicle. In this way, wave device 425may be involved in wave interactions that result from a personinteracting with the vehicle (e.g., entering the vehicle, passing thevehicle on the street, etc.).

Wave interactions between a wave device 425 and another wave device(e.g., a wave device 410) may occur in a manner that is the same as orsimilar to the exemplary wave interactions described above with respectto wave devices 410, 415, and 420. For example, in addition to thetransmission and/or receipt of a unique identifier, wave interactionsinvolving wave devices 425 may include transmission of a payload 424stored as part of UID profile 423.

Payload 424 may include data to be transmitted to other wave devices tocommunicate additional information. For example, payload 424 may includea message to be transmitted to another wave device. In another example,payload 419 may include a UID receipt history that includes a list ofunique identifiers received by wave device 425. Through transmission ofpayload 424 from a wave device 425 to another wave device, informationassociated with object 421 may be communicated to people through waveinteractions. For example, wave device 425 may transmit informationidentifying object 421 to a person that was near object 421 at a certainpoint in time.

The exemplary disclosed wave devices 410, 415, 420, and 425 may beembodiments of wave devices 110 and 120, configured to communicate witheach other and with data collection device 140 via network 150. FIG. 4further depicts this configuration. In this way, wave devices 410, 415,420, and 425, as well as any other wave devices present in system 100,may communicate with each other in one or more wave interactions thatmay occur as a result of interactions between people, entities, places,and/or objects.

In an exemplary embodiment, wave devices 410, 415, 420, and 425 mayoperate in conjunction with data collection device 140 to record andstore information associated with wave interactions that have occurred.For example, wave devices 410, 415, 420, and 425 may store as part ofUID profiles 408, 413, 418, and 423 information associated with a waveinteraction. For example, a wave device may store a unique identifier(which may include a received UID receipt history) received as a resultof a wave interaction with another wave device.

In addition or alternatively, wave devices 410, 415, 420, and 425 maycommunicate with data collection device 140 to store informationassociated with wave interactions. As shown in FIG. 4, in someembodiments, data collection device 140 may include UID profiles 432,434, 436, and 438, which may be respectively associated with uniqueidentifiers 406, 411, 416, and 421. Data collection device 140 maycommunicate with wave devices 410, 415, 420, and 425 to shareinformation associated with wave interactions. In one example, datacollection device 140 may store as part of UID profiles 432-438 UIDreceipt histories associated with each respective unique identifier 406,411, 416, and 421.

In another example, data collection device 140 may store as part of UIDprofiles 432-438 information that may be used to determine an action tobe triggered based upon receipt of a unique identifier by a wave device.For example, UID profile 432 may include information that is used todetermine an action to be triggered by wave device 410 based on a wavedevice 410 receiving unique identifier 411. In addition oralternatively, UID profile 413 may include information that is used todetermine an action to be triggered by wave device 410 based on wavedevice 410 receiving unique identifier 411. In this way, informationfrom multiple UID profiles may be combined to determine an action to betriggered. The information may include programs and/or data that may betransmitted to a wave device for performance of the triggered action.For example, the action may be the display of textual data and theinformation may include the textual data and instructions for displayingthe textual data.

In addition, data collection device 140 (and/or a wave device 410, 415,420, 426) may perform one or more processes to determine additionalinformation based on information stored in associated with one or moreUID profiles. For example, data collection device 140 may analyze aunique identifier in relation to another unique identifier to determineif there is a relationship between the underlying people, entities,places, and/or objects. In another example, data collection device 140may search UID receipt histories to determine which UID profiles includea particular unique identifier.

Exemplary disclosed embodiments of system 100 and UID system 400 allowinteractions between people, entities, places, and objects to take placeas wave interactions through wave devices. Associating the people,entities, places, and objects each with a unique identifier allows thewave interaction to be a reflection of the interaction, since thetransmission and/or receipt of a unique identifier may be directlyrelated to the interaction. For example, an interaction may be a personcoming into a close proximity to another person. Each person may possessa wave device, configured to automatically connect to each other andexchange unique identifiers. In this way, while the people may walk pasteach other without physically communicating, their wave devices mayvirtually “wave” to each other, reflecting and recording the fact thatat that particular time, the two people were near each other.

FIG. 5 shows a flowchart of an exemplary automatic wave interactionprocess 500, consistent with disclosed embodiments. In one embodiment,wave device 110 may perform one or more operations of process 500 toperform a wave interaction with wave device 120. It should be understoodthat wave devices 110 and 120 may be any of wave devices 410, 415, 420,and 425, depending on the interaction that causes process 400. Forexample, wave devices 110 and 120 may be associated with uniqueidentifiers associated with people.

Wave device 110 may detect and connect to a network (step 510). Forexample, one or more components of wave device 110 may be configured toreceive network signals such that wave device 110 may detect that anetwork or direct connection is within range. As has been described, thenetwork may be network 150, which may be a local connection usingBluetooth®, WIFI, or other conventional network. Wave device 110 mayconnect to the network in a conventional manner.

Wave device 110 may identify a computing device via the connectednetwork (step 520). For example, wave device 119 may identify wavedevice 120 through network 150, which may be, for instance, a Bluetooth®connection or a WiFi connection. In an exemplary embodiment, wave device110 may identify a computing device based at least in part on proximitybetween the devices. For example, wave device 110 may connect to wavedevice 120 when wave device 110 and wave device 120 are located within acertain proximity to each other (e.g., a proximity that results in aBluetooth® connection, WiFi connection, NFC communication, etc. Itshould be understood that steps 510 and 520 encompass connections inwhich wave device detects and connects to another computing devicewithout first detecting a network (i.e., detection and connection toanother computing device constitutes detection and connection to anetwork). Once a connection is established, wave device 110 may attemptto communicate with wave device 120 to perform a wave interaction.

Wave device 110 may “wave” to wave device 120 (step 530). For example,wave device 110 may transmit a unique identifier associated with wavedevice 110 (hereinafter “UID110”) to wave device 120. In addition, wavedevice 110 may look for a “wave back” from wave device 120. For example,wave device 110 may boost power to a communication device and look for asignal transmitted to wave device 110.

Wave device 110 may receive a “wave back” from wave device 120 (step540). For example, wave device 110 may receive a unique identifiertransmitted from wave device 120 to wave device 110. The received uniqueidentifier may be a unique identifier associated with wave device 120(hereinafter “UID120”). After step 540, wave device 110 may havereceived UID120 and wave device 120 may have received UD110.

In addition to exchanging unique identifiers, wave device 110 mayexchange additional information with wave device 120 (step 550). Forexample, wave device 110 may transmit a payload to (hereinafter“outgoing payload”) and receive a payload from (hereinafter “incomingpayload”) wave device 120. In an exemplary embodiment, the outgoingpayload may include a UID receipt history associated with UID110 (e.g.,a list of unique identifiers previously received by a wave device (e.g.,wave device 110) as a result of a wave interaction involving UID110).Similarly, the incoming payload may include a UID receipt historyassociated with UID120 (e.g., a list or unique identifiers previouslyreceive by a wave device (e.g., wave device 120) as a result of a waveinteraction involving UID120.

In another example, the outgoing and incoming payloads may include oneor more messages. The one or more messages may be, for example, textualdata, image data, video data, audio data, program instructions, and/orthe like. For example, wave device 110 may transmit an outgoing payloadto wave device 120 that includes data and/or programs that wave device120 may use to display a textual message to a user. The incoming payloadmay similarly include data and/or programs that wave device 110 may useto provide information to a user of wave device 110.

In some embodiments, wave device 110 (and/or wave device 120) may storea default payload to be transmitted to another device during a waveinteraction. In other embodiments, wave device 110 (and/or wave device120) may customize a payload to be transmitted to another device basedon a unique identifier received. For example, wave device 110 mayperform one or more processes to match a received unique identifier(e.g., UID120) to stored information and customize a message to beincluded in a payload to be sent to wave device 120.

After wave device 110 and wave device 120 exchange payloads, process 500may end. As a result of process 500, wave device 110 may have receivedUID120, wave device 120 may have received UID110, and wave devices 110and 120 may have exchanged payloads. In this way, two computing devices,such as mobile devices, may facilitate communication based on proximityto each other. For example, when two people are near each other (e.g.,co-workers passing in the hallway), associated computing devices mayconnect to each other and complete a wave interaction to exchange uniqueidentifiers and payloads as a result.

In addition, wave device 110 and/or wave device 120 may storeinformation to record the wave interaction. For example, wave device 110may record the time, date, and location of a wave interaction, as wellas a received unique identifier (e.g., UID120) and a received payload,including a UID receipt history (e.g., by adding unique identifiers ofthe UID receipt history to a UID receipt history associated with wavedevice 110). As has been described, wave device 110 may store recordedinformation as part of a UID profile (e.g., a UID profile associatedwith UID110).

Further, wave device 110 may communicate with data collection device 140to further use, store, and analyze information associated with a waveinteraction. For example, wave device 110 may transmit informationassociated with one or more wave interactions to data collection device140 over network 150 (e.g., via an Internet connection). Data collectiondevice 140 may perform one or more processes with information receivedfrom wave device 110 (and/or another wave device).

FIG. 6 depicts an exemplary wave interaction enhancing process 600,consistent with disclosed embodiments. In one embodiment, datacollection device 140 may perform process 600 to provide enhancedfunctionality to wave interactions performed by one or more wavedevices. For example, data collection device 140 may store informationidentifying when and where wave interactions occurred and use storedinformation to provide one or more utilities using the information.

Data collection device 140 may connect to wave device 110 (step 610).For example, data collection device 140 and wave device 110 may connectto each other over network 150, which may include an Internetconnection. After connecting, data collection device 140 may identify aUID profile that is associated with wave device 110 (e.g., UID profile432). The UID profile may correspond to a person, entity, place, orobject associated with wave device 110.

In addition, data collection device 140 may receive information fromwave device 110 (step 620). In an exemplary embodiment, data collectiondevice 140 may receive one or more unique identifiers that were receivedby wave device 110 during one or more wave interactions. In someembodiments, data collection device 140 may receive additionalinformation, such as when and where each unique identifier was received,and whether a unique identifier was received as part of a “wave” or“wave back” or if it was part of a UID receipt history received as partof a payload. Data collection device 140 may use the unique identifiersto perform additional functions.

Data collection device 140 may analyze received information to determineif a new unique identifier has been received (step 630). A new uniqueidentifier may be a unique identifier that is not part of a UID receipthistory stored as part of the UID profile corresponding to wave device110. The UID receipt history may include all unique identifierspreviously received and added to the UID profile, excluding those thathave since expired (unique identifiers may include associated expirationtimes, at which point a unique identifier may be removed from a UIDreceipt history). If a new unique identifier has not been received (step630—NO), data collection device may stop process 600 and awaitinstructions associated with user interaction with information stored bydata collection device 140 (step 640).

If, however, a new unique identifier is found (step 630—YES), datacollection device 140 may record the unique identifier with the UIDprofile (step 650). For example, data collection device 140 may add thenew unique identifier to a UID receipt history stored as part of the UIDprofile. In this way, the UID receipt history may be updated to includeunique identifiers that were received by wave device 110. In someembodiments, data collection device 140 may also synchronize the UIDreceipt history with a UID receipt history stored by wave device 110,including removing any expired unique identifiers from the UID receipthistory stored by wave device 110. In this way, wave device 110 maystore an updated UID receipt history for use in subsequent waveinteractions (e.g., where the UID receipt history is transmitted toanother device as part of a payload).

In addition or alternatively, data collection device 140 may match thenew unique identifier to stored information to determine if an action istriggered (step 660). For example, data collection device 140 may matcha received new unique identifier to a UID profile associated with theunique identifier. Data collection device 140 may analyze informationstored as part of the UID profile to determine if an action should betriggered. An action that may be triggered, for example, may includedata collection device 140 transmitting a message (e.g., data and/orprograms) to wave device 110.

Data collection device 140 may determine whether an action should betriggered based on information stored as part of a UID profileassociated with wave device 110 and/or a UID profile associated with theunique identifier determined to be new. For example, data collectiondevice 140 may determine an action should be triggered based on arelationship between the people, entities, places, and/or objectsassociated with the corresponding unique identifiers. For instance, datacollection device 140 may determine that a new received uniqueidentifier is associated with a person that is a friend of a personassociated with wave device 110 (e.g., since the person is in a contactlist stored in wave device 110). Data collection device 140 maydetermine that an action should be triggered to transmit information(e.g., instructions for triggering the action) to wave device 110 toallow wave device 110 to indicate to a user that they were involved in awave interaction with the friend (e.g., “You walked near your friend onMain Street at 3:00 p.m.”).

If data collection device 140 determines that no action is triggered bya received unique identifier (step 660—NO), data collection device 140may return to analyzing the received unique identifiers to determine ifany others are new. If data collection device 140 determines that anaction is triggered by a received unique identifier (step 660—YES), datacollection device 140 may trigger the action (step 670). For example,data collection device 140 may transmit instructions to wave device 110to for triggering the action, which may include information to bedisplayed to a user. The information may include, for example, anidentity of persons, entities, places, and/or objects associated withunique identifiers that were received. For example, wave device 110 mayreceive and provide links to social media profiles, websites, etc.associated with the persons, entities, places, and/or objects identifiedas being associated with a received unique identifier.

Data collection device 140 may then determine whether any other receivedunique identifiers are new. This cycle may repeat until all new uniqueidentifiers are found and any corresponding actions are triggered. Inthis way, a user of wave device 110 may be provided with context to thevarious interactions that occurred during a particular time period. Forexample, wave device 110 may indicate people that a user was close to,entities that the user interacted with, places the user visited, and/orobjects the person was near. Data collection device 140 may subsequentlyawait instructions corresponding to user interaction.

Through exemplary process 600, data collection device 140 may provideadditional functionality to UID system 400. For example, enhancedfunctions may be made possible and/or more feasible since datacollection device 140 may be a server or other computing device thatincludes sufficient memory to store multiple UID profiles. In this way,information associated with multiple UID profiles may be combined todetermine an action to be triggered based on a wave device associatedwith one unique identifier receiving a different unique identifierthrough a wave interaction. In addition, UID receipt histories may bemaintained and stored in a central location, allowing all receivedunique identifiers to be included (even though multiple wave devices mayhave received them).

In some instances, data collection device 140 may receive a uniqueidentifier as a result of an automatic wave interaction process, such asprocess 500. However, it should be understood that data collectiondevice 140 may receive a unique identifier associated with anon-automatic wave interaction. For instance a user may operate wavedevice 110 and input information associated with an interaction thatpreviously occurred. For example, the user may input informationindicating that he or she was present at a meeting earlier in the day,providing identifying information associated with the meeting (e.g.,when and where the meeting occurred, others present at the meeting,and/or a unique identifier associated with the meeting). Wave device 110may receive or determine a unique identifier associated with the meeting(e.g., a unique identifier associated with a room in which the meetingoccurred), which may constitute a wave interaction. Wave device 110 maytransmit this unique identifier, as well as other input information, todata collection device 140 as part of process 600. In this way, if aninteraction occurs but a wave device does not automatically perform awave interaction (e.g., because the wave device is not present at thetime or is not functioning properly), information associated with theinteraction may be manually provided.

In one aspect, one or more computing devices may perform processes 500and/or 600 to record information associated with interactions that occurbetween persons, entities, places, and/or objects. For example, a personassociated with and carrying wave device 110 may pass another personassociated with and carrying wave device 120. Wave device 110 and wavedevice 120 may connect to each other and perform a wave interaction,such as that described with respect to process 500. Each wave device110, 120 and/or data collection device 140 may record informationassociated with the wave interaction, including a date, time, and placeat which the underlying interaction occurred. In this way, each personmay access information indicating that they were near the other person,even though they may not have been aware of it. As these interactionsoccur across many wave devices, a complex database of wave interactionsmay be created, allowing for various functions that may not otherwise bepossible.

In one example, an entity (e.g., a business, school, etc.) may use oneor more wave devices to track attendance at certain events. Forinstance, a business may position a wave device in a conference room. Asemployees enter the conference room, wave devices associated with theemployees may perform wave interactions with the conference room wavedevice. In this way, the interaction of the employee with the conferenceroom may be recorded, along with the time and date of the meeting, suchthat a list of meeting attendees may be stored and subsequently accessedby users associated with the entity (e.g., management, the employees,etc.).

Similarly, one or more computing devices may combine informationrecorded as a result of a wave interaction with other information toprovide a user with information regarding interactions that occurthroughout their day. For example, a user may operate a wave device toconnect the wave device to data collection device 140, which mayassociate received unique identifiers with identities of persons,entities, places, and/or objects. These identities may be provided backto the wave device and displayed, allowing the user to learn and/or bereminded of interactions with which they were involved.

Further, the association of unique identifiers with entities, places,and objects allows for more complex wave interactions to occur,encompassing interactions that may only involve one person. For example,customers that enter a retail store, tourists that visit a monument, andpassengers that enter vehicles may constitute interactions, allowing formore wave interactions to occur and additional information to berecorded and used in subsequent analyses.

In addition, the transmission and receipt of UID receipt histories aspart of a wave interaction may allow a unique identifier to travelthroughout several wave interactions. For example, a unique identifierassociated with a first person may be initially transmitted to a wavedevice associated with a second person when the two people walk pasteach other. The wave device associated with the second person may addthe unique identifier to a UID receipt history, which may be transmittedto another wave device during a subsequent wave interaction. Forexample, the second person may visit a retail store of an entity that isassociated with a wave device. The entity's wave device may perform awave interaction with the wave device associated with the second person,receiving the unique identifier associated with first person as a result(via the UID receipt history). The entity's wave device may subsequentlytransmit the first person's unique identifier to another wave device,such as a wave device associated with yet another person (e.g., anothercustomer in the store). This process may continuously repeat such thatthe first person's unique identifier is received by many wave devicesthrough different wave interactions, until the first person resets theirunique identifier or it expires.

Further, the disclosed embodiments allow for a broad range ofapplications that utilize wave interactions as a means to facilitatecommunication. In particular, the recording of information associatedwith wave interactions, including the transmission of payloads thatinclude UID receipt histories, allows a device to track a uniqueidentifier as it is used in various wave interactions. For example, auser may operate a wave device (or other computing device) to access anassociated UID profile stored by data collection device 140. As waveinteractions involving a unique identifier associated with the useroccur, information associated with those wave interactions may be storedas part of the UID profile. The user may operate the wave device tocommunicate with data collection device 140, and provide instructions toanalyze the UID profile for specific information.

For example, data collection device 140 may analyze the UID profile tocalculate statistics associated with the user's unique identifier. Thestatistics may include, for example, information associated with uniqueidentifiers stored as part of the UID profile's UID receipt history. Thestatistics may indicate, for example, that the UID receipt historyincludes a certain number of unique identifiers associated withparticular categories, such as the number of friends of the user, thenumber of co-workers of the user, the total number of unique identifiersreceived, etc. The statistics may also include information associatedwith the number of unique identifiers.

In another example, data collection device 140 may analyze the UIDprofile to identify unique identifiers that were received as part of awave or wave back and not only as part of UID receipt history(indicating that the unique identifier is associated with a person,entity, place, or object with which the user interacted), and todetermine whether there is a relationship between those persons,entities, places, or objects and the user warranting the providing ofadditional information. For example, data collection device 140 mayidentify received unique identifiers associated with matchmakingprofiles that are a match for the user's matchmaking profile. Datacollection device 140 may provide a notification to a wave device toinform the user of the match and allow the user to follow up (e.g., senda message) if desired. In this way, additional interaction betweenpeople that previously interacted (even if unknowingly) may beencouraged and effectiveness of certain interactions (e.g., onlinedating) may be improved.

Even further, data collection device 140 may determine informationassociated with wave devices that correspond to UID profiles thatcurrently include UID receipt histories that include the user's uniqueidentifier. For example, data collection device 140 may identify that auser's unique identifier, through one or more wave interactions, hasmade its way to a wave device associated with a particular place (e.g.,the Eiffel Tower). In another example, data collection device maydetermine that the unique identifier is in a UID receipt historyassociated with a wave device associated with a person and that thatwave device is located in a particular location (e.g., at a concertvenue). Data collection device 140 may identify this information and mayprovide it to a wave device for display (e.g., to the user associatedwith the unique identifier).

In addition, data collection device 140 and/or any number of wavedevices may be used in one or more wave interaction activities. Forexample, a group of people may implement a “race” to determine whoseunique identifier will arrive at a particular location first. Eachunique identifier may take a path to the location through wave devices,as the unique identifier is transmitted through wave devices in waveinteractions as part of a UID receipt history. Data collection device140 may track the “race” and notify wave devices of the results. The“race” may include data collection device 140 analyzing informationassociated with wave interactions between wave devices that have alreadybeen established and/or wave interactions that will occur after the“race” begins. A similar wave interaction activity may include trackinga unique identifier as it is transmitted to a specific wave device, suchas to determine how many wave interactions are needed for the specifieddestination to be reached.

In another exemplary wave interaction activity, a virtual “sonar ping”may be conducted. The “sonar ping” may include data collection device140 determining a boundary around a location of some or all wave devicesthat have received a particular unique identifier. In this way, datacollection device 140 may provide a user with a graphical representationof how far their unique identifier has “traveled”.

Data collection device 140 may allow for additional functionality thatfurther allows a user to manage their unique identifier. For example,data collection device 140 may be configured to “reset” a uniqueidentifier, such as to remove the unique identifier from at least someUID receipt histories. In this way, a unique identifier may be re-usedin one or more wave interaction activities, such as those describedabove, which may not otherwise be possible or practical because of theunique identifiers presence in one or more UID receipt histories.

Through the exemplary disclosed embodiments, computing devices maycommunicate with each other through wave interactions that reflectunderlying interactions between people, entities, places, and objects.The wave interactions may be recorded and used in one or more processesto provide users with information related to interactions that occurred,whether or not they were aware of or even involved in the interaction.

The exemplary disclosed embodiments describe systems and methods forusing a unique identifier to facilitate communication. The foregoingdescription has been presented for purposes of illustration. It is notexhaustive and is not limited to the precise forms or embodimentsdisclosed. Modifications and adaptations of the embodiments will beapparent from consideration of the specification and practice of thedisclosed embodiments. For example, the described implementationsinclude hardware and software, but systems and methods consistent withthe present disclosure can be implemented as hardware alone.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. For example, program sections or program modulescan be designed in or by means of Java, C, C++, assembly language, orany such programming languages. One or more of such software sections ormodules can be integrated into a computer system, computer-readablemedia, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

1-21. (canceled)
 22. A data collection device, comprising: one or more memory devices storing information and instructions; and one or more processors configured to execute the instructions to: connect with a wave device and receive from the wave device a unique identifier that identifies a person, entity, place, or object associated with the wave device; retrieve, based on the received unique identifier, a profile associated with the wave device, wherein the profile corresponds to the person, entity, place, or object associated with the wave device; receive information from the wave device, the received information including one or more unique identifiers, associated with one or more other wave devices, received by the wave device during one or more wave interactions with the one or more other wave devices; determine if the received information includes a new unique identifier not included in the profile associated with the wave device; add the new unique identifier to the profile associated with the wave device upon determining that the received information includes the new unique identifier; and determine whether an action should be triggered based on the new unique identifier and the profile associated with the wave device.
 23. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to analyze the profile associated with the wave device to calculate statistics associated with the new unique identifier.
 24. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to analyze the profile associated with the wave device to determine if the one or more unique identifiers are received as part of a wave received from one of the one or more other wave devices or a wave back received from one of the one or more other wave devices in response to a wave from the wave device.
 25. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to analyze relationships between the new unique identifier and the one or more unique identifiers associated with the one or more other wave devices to determine whether an action should be triggered.
 26. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to record the received information comprising a time, a date, and a location of the one or more wave interactions associated with the one or more received unique identifiers and to store the recorded information as a part of the profile associated with the wave device.
 27. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to store a historical list of the one or more unique identifiers received by the wave device.
 28. The device of claim 22, wherein the one or more processors are further configured to execute the instructions to assign the unique identifier to the person, entity, place, or object associated with the wave device.
 29. The device of claim 27, wherein the one or more processors are further configured to execute the instructions to reset one of the one or more unique identifiers to remove the one of the one or more unique identifiers from the historical list.
 30. The device of claim 27, wherein the one or more processors are further configured to execute the instructions to synchronize the historical list with a historical list, stored by the wave device, to remove any unexpired unique identifiers in the historical list stored by the wave device.
 31. A computer-implemented method of device communication, the method comprising: a data collection device connecting, by one or more processors, with a wave device and receiving from the wave device a unique identifier that identifies a person, entity, place, or object associated with the wave device; retrieving, based on the received unique identifier, a profile associated with the wave device, wherein the profile corresponds to the person, entity, place, or object associated with the wave device; receiving information from the wave device, the received information including one or more unique identifiers, associated with one or more other wave devices, received by the wave device during one or more wave interactions with the one or more other wave devices; determining if the received information includes a new unique identifier not included in the profile associated with the wave device; adding the new unique identifier to the profile associated with the wave device upon determining that the received information includes the new unique identifier; and determining whether an action should be triggered based on the new unique identifier and the profile associated with the wave device.
 32. The method of claim 31, wherein the method further comprises analyzing the profile associated with the wave device to calculate statistics associated with the new unique identifier.
 33. The method of claim 31, wherein the method further comprises analyzing the profile associated with the wave device to determine if the one or more unique identifiers are received as part of a wave received from one of the one or more other wave devices or a wave back received from one of the one or more other wave devices in response to a wave from the wave device.
 34. The method of claim 31, wherein the method further comprises analyzing relationships between the new unique identifier and the one or more unique identifiers associated with the one or more other wave devices to determine whether an action should be triggered.
 35. The method of claim 31, wherein the method further comprises recording the received information including a time, date, and location of the one or more wave interactions associated with the one or more received unique identifiers and store the recorded information as a part of the profile associated with the wave device.
 36. The method of claim 31, wherein the method further comprises storing a historical list of the one or more unique identifiers received by the wave device.
 37. The method of claim 31, wherein the method further comprises assigning the unique identifier to the person, entity, place, or object associated with the wave device.
 38. The method of claim 36, wherein the method further comprises resetting one of the one or more unique identifiers to remove the one of the one or more unique identifiers from the historical list.
 39. The method of claim 36, wherein the method further comprises synchronizing the historical list with a historical list, stored by the wave device, to remove any unexpired unique identifiers in the historical list stored by the wave device.
 40. A non-transitory computer-readable medium storing instructions executable by a processor to perform operations at a data collection device, the operations comprising: connecting with a wave device and receiving from the wave device a unique identifier that identifies a person, entity, place, or object associated with the wave device; retrieving, based on the received unique identifier, a profile associated with the wave device, wherein the profile corresponds to the person, entity, place, or object associated with the wave device; receiving information from the wave device, the received information including one or more unique identifiers, associated with one or more other wave devices, received by the wave device during one or more wave interactions with the one or more other wave devices; determining if the received information includes a new unique identifier not included in the profile associated with the wave device; adding the new unique identifier to the profile associated with the wave device upon determining that the received information includes the new unique identifier; and determining whether an action should be triggered based on the new unique identifier and the profile associated with the wave device.
 41. The non-transitory computer-readable medium of claim 40, wherein the operations further comprise analyzing the profile associated with the wave device to calculate statistics associated with the new unique identifier. 